home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Shareware Overload Trio 2
/
Shareware Overload Trio Volume 2 (Chestnut CD-ROM).ISO
/
dir40
/
noecho2.zip
/
NOECHO2.DOC
< prev
next >
Wrap
Text File
|
1988-03-28
|
3KB
|
70 lines
DEFAULT OF "ECHO OFF" FOR PC DOS 2.0/2.1/3.1/3.2/3.3
----------------------------------------------------
For all those "Front-End Writers" that can't stand to have to put
ECHO OFF followed by CLS at the top of a batch file and then see the
ECHO OFF come up on the screen, these little patches to PC DOS 2.0 through
3.3 COMMAND.COM are just what you need. They make ECHO OFF the default
condition for all batch files when they are run and the line
E 096E 00 (Dos 2.X ONLY)
E 1967 00 (Dos 3.1 ONLY)
E 1B2C 00 (Dos 3.2 ONLY)
E 1D68 00 (Dos 3.3 ONLY)
in the patch file makes ECHO OFF the default condition at boot time when
AUTOEXEC.BAT is run. If you want the default at boot time to remain as
ECHO ON then use your text editor to take this line out of the patch
file.
Please note that the patch files will ONLY work for their
respective versions of PC DOS, as the COMMAND.COM for PC DOS 2.0 and 2.1
are somewhat different.
Use NOECHO20.BAT for PC DOS 2.0
Use NOECHO21.BAT for PC DOS 2.1
Use NOECHO31.BAT for PC DOS 3.1
Use NOECHO32.BAT for PC DOS 3.2
Use NOECHO33.BAT for PC DOS 3.3
To run the patch files, just make sure you have a copy of DEBUG.COM
and the respective version of COMMAND.COM on the same disk (and in the
same directory). Then type either NOECHO20 or NOECHO21 or NOECHO32 or
NOECHO33 as appropriate. As DEBUG uses the contents of the batch file
which calls it for data to do the patch you will see a couple of error
indications as DEBUG tries to make sense out of the first two lines of
the file. These won't hurt anything.
When you are back at the DOS prompt, use the new COMMAND.COM to
re-boot your system with, and voila! Note that if you intend using the
patched version you have made, you should go through ALL your disks that
have that version of COMMAND.COM on them and replace it with the new
patched copy if you want to avoid the annoying "Illegal COMMAND.COM ..."
messages that appear when DOS tries to reload old unpatched copies of
COMMAND.COM.
The original data on the DOS 2.0 patch came from a source that I
don't remember. I cleaned it up a little so the error message that the
little patch subroutine is written into didn't look so ragged, and added
the patch for ECHO OFF at boot time. I then examined PC DOS 2.1 and 3.2
and 3.3 COMMAND.COMs and adapted the patch to them.
Anyway, enjoy your new freedom of choice!
Editor's note:
I got the above for 2.0/2.1/3.2/3.3 from the PDSE bulletin board.
Since I run DOS 3.1 to keep my memory usage down, I adapted the patches
to 3.1 and added the result to the documentation and batch set.
As far as I have been able to determine, you STILL need an ECHO OFF at
the start of your AUTOEXEC.BAT file, but after that, ECHO OFF will be the
default for batch files under these patches.